Method, device, and computer program product for obtaining diagnostic information

ABSTRACT

Techniques may involve determining, according to determination that a received system alarm corresponds to a predefined to-be-monitored alarm, the received system alarm as a target system alarm. The techniques may further involve determining a system module corresponding to the target system alarm based on a predefined mapping relationship between the system alarm and the system module. In addition, the techniques may further involve acquiring the system diagnostic information of the system module which is associated with the target system alarm. In this way, time for collecting system diagnostic information can be reduced and user experience can be improved.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Chinese Patent Application No.CN202010225309.6, on file at the China National Intellectual PropertyAdministration (CNIPA), having a filing date of Mar. 26, 2020, andhaving “METHOD, DEVICE, AND COMPUTER PROGRAM PRODUCT FOR OBTAININGDIAGNOSTIC INFORMATION” as a title, the contents and teachings of whichare herein incorporated by reference in their entirety.

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to the field ofcomputer networks, and in particular, to a method and an electronicdevice for acquiring system diagnostic information, and a computerprogram product.

BACKGROUND

When an abnormality or failure occurs in a system, a user usually feedsfailure information back to a system developer. In order to solve thesystem abnormality or failure, the system developer usually collectsdiagnostic information related to the system abnormality or failure froman on-site technical support professional, and the on-site technicalsupport professional may also attempt to acquire relevant test data byreproducing the system abnormality and failure. These tasks require theon-site technical support professional to contact the user multipletimes for collecting diagnostic information sufficient to solve thesystem abnormality or failure. Therefore, this multi-party communicationprocess usually takes a long time and requires a lot of human resources.In addition, due to the need for repeated communications and theexcessive long period for problem solving, it is likely to result inpoor user experience.

SUMMARY OF THE INVENTION

Embodiments of the present disclosure relate to a method and a devicefor acquiring system diagnostic information, and a computer programproduct.

In a first aspect of the present disclosure, a method for acquiringsystem diagnostic information is provided. The method may includedetermining, according to determination that a received system alarmcorresponds to a predefined to-be-monitored alarm, the received systemalarm as a target system alarm. The method may further includedetermining a system module corresponding to the target system alarmbased on a predefined mapping relationship between the system alarm andthe system module. In addition, the method may further include acquiringthe system diagnostic information of the system module which isassociated with the target system alarm.

In a second aspect of the present disclosure, an electronic device isprovided. The device includes: at least one processing unit; and atleast one memory coupled to the at least one processing unit and storinginstructions configured to be executed by the at least one processingunit, wherein when executed by the at least one processing unit, theinstructions cause the device to perform actions including: determining,according to determination that a received system alarm corresponds to apredefined to-be-monitored alarm, the received system alarm as a targetsystem alarm; determining a system module corresponding to the targetsystem alarm based on a predefined mapping relationship between thesystem alarm and the system module; and acquiring the system diagnosticinformation of the system module which is associated with the targetsystem alarm.

In a third aspect of the present disclosure, a computer program productis provided. The computer program product is tangibly stored in anon-transitory computer-storage medium and including machine-executableinstructions. When executed by a device, the machine-executableinstructions cause the device to perform any step of the methoddescribed according to the first aspect of the present disclosure.

The summary is provided to introduce the choice of concepts in asimplified form, which will be further described in the followingDetailed Description. The summary is neither intended to identify keyfeatures or necessary features of the present disclosure, nor intendedto limit the scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objectives, features, and advantages of the presentdisclosure will become more apparent based on a more detaileddescription of example embodiments of the present disclosure withreference to the accompanying drawings, wherein identical referencenumerals generally represent identical components in the exampleembodiments of the present disclosure.

FIG. 1 is a schematic diagram of an example environment in whichembodiments of the present disclosure can be implemented;

FIG. 2 is a flowchart of a process for acquiring system diagnosticinformation according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of an example process for acquiring systemdiagnostic information according to an embodiment of the presentdisclosure;

FIG. 4 is a flowchart of an example process for generating detectiondata as system diagnostic information according to an embodiment of thepresent disclosure; and

FIG. 5 is a schematic block diagram of an example device that can beconfigured to implement an embodiment of the present disclosure.

Identical or corresponding numerals represent identical or correspondingparts in various drawings.

DETAILED DESCRIPTION

The individual features of the various embodiments, examples, andimplementations disclosed within this document can be combined in anydesired manner that makes technological sense. Furthermore, theindividual features are hereby combined in this manner to form allpossible combinations, permutations and variants except to the extentthat such combinations, permutations and/or variants have beenexplicitly excluded or are impractical. Support for such combinations,permutations and variants is considered to exist within this document.

It should be understood that the specialized circuitry that performs oneor more of the various operations disclosed herein may be formed by oneor more processors operating in accordance with specialized instructionspersistently stored in memory. Such components may be arranged in avariety of ways such as tightly coupled with each other (e.g., where thecomponents electronically communicate over a computer bus), distributedamong different locations (e.g., where the components electronicallycommunicate over a computer network), combinations thereof, and so on.

Preferred embodiments of the present disclosure will be described inmore detail below with reference to the accompanying drawings. Althoughthe preferred embodiments of the present disclosure are shown in theaccompanying drawings, it should be appreciated that the presentdisclosure can be implemented in various forms and should not be limitedby the embodiments described here. In contrast, the embodiments areprovided to make the present disclosure more thorough and complete, andto fully convey the scope of the present disclosure to those skilled inthe art.

The term “include” and its variants as used herein indicatenon-exclusive inclusion, i.e., “including, but not limited to.” Unlessspecifically stated otherwise, the term “or” indicates “and/or.” Theterm “based on” indicates “based at least in part on.” The terms “anexample embodiment” and “an embodiment” indicate “at least one exampleembodiment.” The term “another embodiment” indicates “at least oneadditional embodiment.” The terms “first,” “second,” and the like mayrefer to different or identical objects. Other explicit and implicitdefinitions may also be included below.

As mentioned above, in a conventional process of collecting systemdiagnostic information, a system developer usually collects diagnosticinformation related to system abnormality or failure through an on-sitetechnical support professional, and the on-site technical supportprofessional needs to contact a user possibly multiple times forcollecting system diagnostic information sufficient to solve the systemabnormality or failure. This kind of manual feedback mechanism based onoperators (such as the user and the technical support professional) hasthe disadvantages of being time-consuming and complicated, and wastinghuman resources.

In order to solve the above problems and improve user experience, amechanism for automatically collecting system diagnostic information isproposed in an example embodiment of the present disclosure, and thecollected system diagnostic information may be subdivided for specificmodules in the system, so as to provide system developers of the moduleswith a reliable basis as much as possible for debugging the system.

FIG. 1 is a schematic diagram of an example environment in whichembodiments of the present disclosure can be implemented. In exampleenvironment 100, system alarm 110 can alert a user that a potentialproblem exists in the system or a problem event is happening in thesystem. It should be appreciated that the above example is merelydescription of the present disclosure, but not a specific limitation tothe present disclosure.

As shown in FIG. 1, system alarm 110 is input to computing device 120for effectively utilizing system alarm 110. In some embodiments,computing device 120 may include, but is not limited to, a personalcomputer, a server computer, a handheld or laptop device, a mobiledevice (such as a mobile phone, a personal digital assistant (PDA), anda media player), a multiprocessor system, a consumer electronic product,a small computer, a mainframe computer, a distributed computingenvironment including any of the above systems or devices, and the like.

After processing by computing device 120, system diagnostic information130 corresponding to system alarm 110 may be collected based on systemalarm 110. All system diagnostic information 130 for analysis will bequickly collected after system alarm 110 is generated. By usingcollected system diagnostic information 130, a developer no longer needsto wait for a long time, thus saving a lot of time and a lot of humanresources.

It should be appreciated that the environment shown in FIG. 1 is merelyby way of example, but not a specific limitation to the presentdisclosure. The number and structure of components and the arrangementof the environment in the embodiment shown in FIG. 1 are examples fordescription, and are not intended to limit the present disclosure in anyway.

FIG. 2 is a flowchart of process 200 for acquiring system diagnosticinformation 130 according to an embodiment of the present disclosure. Insome embodiments, process 200 may be performed by computing device 120in FIG. 1. As an example, process 200 may be implemented in exampleenvironment 100 shown in FIG. 1. Process 200 for acquiring systemdiagnostic information 130 according to an embodiment of the presentdisclosure will now be described with reference to FIG. 2. For ease ofunderstanding, the specific situations mentioned in the descriptionbelow are by way of example, and are not used to limit the protectionscope of the present disclosure.

In 202, computing device 120 may determine, according to determinationthat received system alarm 110 corresponds to a predefinedto-be-monitored alarm, received system alarm 110 as a target systemalarm. As an example, when computing device 120 receives system alarm110, computing device 120 first determines whether system alarm 110belongs to a to-be-monitored alarm. According to actual needs, a systemdeveloper, an on-site technical support professional, and even a usercan preset system alarms that need to be monitored, and computing device120 is only configured to monitor preset to-be-monitored alarms. Ifsystem alarm 110 belongs to the to-be-monitored alarms, system alarm 110is marked as the target system alarm for subsequent processing. Ifsystem alarm 110 does not belong to the to-be-monitored alarms, process200 exits. In this way, the system developer can purposefully monitorspecific system alarms based on experience. Alternatively, thepredefined to-be-monitored alarms may also be set as all system alarms.In other words, computing device 120 can monitor all system alarms.

In 204, computing device 120 may determine a system module correspondingto the target system alarm based on a predefined mapping relationshipbetween the system alarm and the system module. It should be appreciatedthat any system includes multiple system modules, and each system moduleis developed and maintained by a corresponding system developer.Therefore, the system developer can preset a correspondencerelationship, i.e., a mapping relationship, between each to-be-monitoredsystem alarm and a system module. The mapping relationship may be storedas a database in a storage apparatus that is physically orcommunicatively connected to computing device 120. In this way,computing device 120 may specifically collect diagnostic informationrelated to system alarms. A system developer responsible for developingand maintaining a system module does not need to consult and analyzediagnostic information related to another system module, thereby savinghuman resources.

In 206, computing device 120 may acquire system diagnostic information130 of the system module which is associated with the target systemalarm. In some embodiments, system diagnostic information 130 acquiredby computing device 120 is mainly a system log entry related to thesystem module. Specifically, FIG. 3 is a flowchart of example process300 for acquiring system diagnostic information 130 according to anembodiment of the present disclosure. In some embodiments, process 300may be performed by computing device 120 in FIG. 1. As an example,process 300 may be implemented in example environment 100 shown inFIG. 1. Process 300 for acquiring system diagnostic information 130according to an embodiment of the present disclosure will now bedescribed with reference to FIG. 3. For ease of understanding, thespecific situations mentioned in the description below are by way ofexample, and are not used to limit the protection scope of the presentdisclosure.

In 302, computing device 120 may acquire a system log entry of the abovesystem module which is associated with the target system alarm. In otherwords, once a system alarm is issued by a system, all system log entriesassociated with the system module corresponding to the system alarm arecollected. The system developer can consult the collected system logentries to analyze and process problems in the system.

In 304, computing device 120 may determine system diagnostic information130 based on the system log entry. After all the above system logentries are acquired, computing device 120 may generate systemdiagnostic information 130 in the form of a file from these system logentries. In this way, all required system diagnostic information can becollected after the system alarm is triggered, so that the developer cancollect diagnostic information in a laboratory without the need forlong-term communication with the on-site technical support professionalor even the user, which significantly saves human resources.

It should be appreciated that, in addition to the above manner ofdirectly acquiring system log entries, computing device 120 may alsoacquire detection data by detecting a system module based on a targetsystem alarm, and determine the system diagnostic information based onthe detection data. The above process of acquiring the detection dataneeds to be further described in detail below.

FIG. 4 is a flowchart of example process 400 for generating detectiondata as system diagnostic information according to an embodiment of thepresent disclosure, in which a specific process of collecting systemdiagnostic information 130 is shown. In some embodiments, process 400may be performed by computing device 120 in FIG. 1. As an example,process 400 may be implemented in example environment 100 shown inFIG. 1. Process 400 for generating detection data according to anembodiment of the present disclosure will now be described withreference to FIG. 4. For ease of understanding, the specific datamentioned in the description below are by way of example, and are notused to limit the protection scope of the present disclosure.

In 402, computing device 120 may acquire a system log entry of thesystem module which is associated with the target system alarm. In someembodiments, computing device 120 may enable logging to collect all logentries associated with the target system alarm. As an example, a debuglog of a specific module may be started through a specific instruction.

In 404, computing device 120 may determine an operation associated withthe target system alarm from the system log entry. In some embodiments,in order to reproduce the above problem event associated with the systemalarm, a relevant operation that causes the problem event may bedetermined based on the system log entry. As an example, all packets ofthe system interface can be captured through specific instructions.

In 406, computing device 120 may acquire a state of the system modulewhen the above operations are performed. As an example, if the problemevent is that a user of a network file system (NFS) cannot access an NFSshare, a state of the system module in this situation may be recorded byreproducing the situation. For example, the connectivity of a fileinterface may be checked through a specific instruction; theconnectivity of a server may be checked by a specific instruction; aconfiguration state of a relevant server may be checked by a specificinstruction, and so on.

In 408, computing device 120 may generate detection data based on theabove state. After all the above detection data is acquired, computingdevice 120 may generate system diagnostic information 130 in the form ofa file from the detection data.

In this way, all required system diagnostic information can be collectedvery quickly after the system alarm is triggered. Since the operation isvery close to a time stamp when the problem event occurs, the systemdiagnostic information is highly valuable, and also provides very usefulinformation for a classification operation of different modules, thussaving human resources.

In some embodiments, process 200 may further include outputting systemdiagnostic information 130 for analysis when receiving an eventassociated with the target system alarm which is fed back by the user.In other words, computing device 120 can collect system diagnosticinformation corresponding to different system alarms in real time, andwhen a user feeds back a system alarm, provide system diagnosticinformation corresponding to the system alarm to a system developer.Alternatively, when an on-site technical support professional or atester specifies a certain system alarm, computing device 120 may alsoprovide system diagnostic information corresponding to the system alarmto the system developer.

In some embodiments, the system module may include at least one of astorage module, a display module, a computing module, and a networkmodule.

The above process of collecting system diagnostic information isimplemented based on the system alarm. Alternatively or additionally, itmay also be implemented based on the problem event itself or anothersignal.

With the above embodiments, all required system diagnostic informationcan be collected after a system alarm is received, so that a developercan collect diagnostic information in a laboratory without communicatingto the site for a long time and multiple times, thereby saving time andimproving user experience. In addition, the operation of collectingdiagnostic information is mainly directed to a system module associatedwith the system alarm, the system developer responsible for developingand maintaining a system module does not need to consult and analyzediagnostic information related to another system module, thereby savinghuman resources.

FIG. 5 is a schematic block diagram of example device 500 that can beconfigured to implement an embodiment of the present disclosure. Asshown in the figure, device 500 includes central processing unit (CPU)501 that can perform various appropriate actions and processingaccording to computer program instructions stored in read-only memory(ROM) 502 or computer program instructions loaded from storage unit 508to random access memory (RAM) 503. Various programs and data requiredfor the operation of device 500 can also be stored in RAM 503. CPU 501,ROM 502, and RAM 503 are connected to each other through bus 504.Input/output (I/O) interface 505 is also connected to bus 504.

A plurality of components in device 500 are connected to I/O interface505, including: input unit 506, such as a keyboard and a mouse; outputunit 507, such as various types of displays and speakers; storage unit508, such as a magnetic disk and an optical disc; and communication unit509, such as a network card, a modem, and a wireless communicationtransceiver. Communication unit 509 allows device 500 to exchangeinformation/data with other devices over a computer network such as theInternet and/or various telecommunication networks.

The various processes and processing described above, for example,processes 200, 300, and/or 400, may be performed by processing unit 501.For example, in some embodiments, processes 200, 300, and/or 400 can beimplemented as a computer software program that is tangibly included ina machine-readable medium such as storage unit 508. In some embodiments,some or all of the computer programs can be loaded and/or installed ontodevice 500 via ROM 502 and/or communication unit 509. When the computerprogram is loaded into RAM 503 and executed by CPU 501, one or moresteps of processes 200, 300, and/or 400 described above may beimplemented.

The present disclosure may be a method, an apparatus, a system, and/or acomputer program product. The computer program product may include acomputer-readable storage medium storing computer-readable programinstructions for performing various aspects of the present disclosure.

The computer-readable storage medium may be a tangible device capable ofretaining and storing instructions used by an instruction-executingdevice. For example, the computer-readable storage medium may be, but isnot limited to, an electrical storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any appropriate combination of theabove. More specific examples (a non-exhaustive list) of thecomputer-readable storage medium include: a portable computer disk, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or flash memory), a staticrandom access memory (SRAM), a portable compact disk read-only memory(CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk,a mechanical coding device such as a punch card or protrusions in agroove on which instructions are stored, and any appropriate combinationof the above. The computer-readable storage medium as used here is notexplained as transient signals themselves, such as radio waves or otherelectromagnetic waves propagated freely, electromagnetic wavespropagated through waveguides or other transmission media (e.g., lightpulses propagated through fiber-optic cables), or electrical signalstransmitted over electrical wires.

The computer-readable program instructions described here may bedownloaded from the computer-readable storage medium to variouscomputing/processing devices or downloaded to external computers orexternal storage devices over a network such as the Internet, a localarea network, a wide area network, and/or a wireless network. Thenetwork may include copper transmission cables, fiber optictransmission, wireless transmission, routers, firewalls, switches,gateway computers, and/or edge servers. A network adapter card ornetwork interface in each computing/processing device receivescomputer-readable program instructions from the network and forwards thecomputer-readable program instructions for storage in thecomputer-readable storage medium in each computing/processing device.

The computer program instructions for performing the operations of thepresent disclosure may be assembly instructions, instruction setarchitecture (ISA) instructions, machine instructions, machine-relatedinstructions, microcode, firmware instructions, state setting data, orsource code or object code written in any combination of one or moreprogramming languages, including object oriented programming languagessuch as Smalltalk and C++, as well as conventional proceduralprogramming languages such as the “C” language or similar programminglanguages. The computer-readable program instructions may be executedcompletely on a user's computer, partially on a user's computer, as aseparate software package, partially on a user's computer and partiallyon a remote computer, or completely on a remote computer or server. Inthe case where a remote computer is involved, the remote computer can beconnected to a user computer over any kind of networks, including alocal area network (LAN) or wide area network (WAN), or can be connectedto an external computer (e.g., connected over the Internet using anInternet service provider). In some embodiments, an electronic circuit,such as a programmable logic circuit, a field programmable gate array(FPGA), or a programmable logic array (PLA), can be customized byutilizing state information of the computer-readable programinstructions. The electronic circuit can execute computer-readableprogram instructions to implement various aspects of the presentdisclosure.

Various aspects of the present disclosure are described here withreference to flowcharts and/or block diagrams of the method, theapparatus (system), and the computer program product implementedaccording to the embodiments of the present disclosure. It should beappreciated that each block in the flowcharts and/or block diagrams anda combination of blocks in the flowcharts and/or block diagrams can beimplemented by computer-readable program instructions.

The computer-readable program instructions can be provided to aprocessing unit of a general purpose computer, a special purposecomputer, or another programmable data processing apparatus to produce amachine, such that the instructions, when executed by the processingunit of the computer or another programmable data processing apparatus,generate an apparatus for implementing the functions/actions specifiedin one or more blocks in the flowcharts and/or block diagrams. Thecomputer-readable program instructions may also be stored in acomputer-readable storage medium, and the instructions cause thecomputer, the programmable data processing apparatus, and/or anotherdevice to work in a specific manner, such that the computer-readablemedium storing the instructions includes an article of manufactureincluding instructions for implementing various aspects offunctions/actions specified by one or more blocks in the flowchartsand/or block diagrams.

The computer-readable program instructions may also be loaded onto acomputer, another programmable data processing apparatus, or anotherdevice, such that a series of operational steps are performed on thecomputer, another programmable data processing apparatus, or anotherdevice to produce a computer implemented process. In this way, theinstructions executed on the computer, another programmable dataprocessing apparatus, or another device implement the functions/actionsspecified in one or more blocks in the flowcharts and/or block diagrams.

The flowcharts and block diagrams in the accompanying drawingsillustrate the architectures, functions, and operations of possibleimplementations of systems, methods, and computer program productsaccording to multiple embodiments of the present disclosure. In thisregard, each block in the flowcharts or block diagrams can represent amodule, a program segment, or a portion of an instruction that includesone or more executable instructions for implementing the specifiedlogical functions. In some alternative implementations, functionslabeled in the blocks may occur in an order different from that aslabeled in the accompanying drawings. For example, two successive blocksmay actually be performed basically in parallel, or they can beperformed in an opposite order sometimes, depending on the functionsinvolved. It should also be noted that each block in the block diagramsand/or flowcharts and a combination of blocks in the block diagramsand/or flowcharts can be implemented using a dedicated hardware-basedsystem for executing specified functions or actions, or can beimplemented using a combination of dedicated hardware and computerinstructions.

Various embodiments of the present disclosure have been described above,and the foregoing description is illustrative rather than exhaustive,and is not limited to the disclosed embodiments. Numerous modificationsand changes are apparent to those of ordinary skill in the art withoutdeparting from the scope and spirit of the illustrated variousembodiments. The selection of terms as used herein is intended to bestexplain the principles and practical applications of the variousembodiments or technical improvements of technologies on the market, orto enable other persons of ordinary skill in the art to understand theembodiments disclosed here.

The invention claimed is:
 1. A method for acquiring system diagnosticinformation, comprising: determining, according to determination that areceived system alarm corresponds to a predefined to-be-monitored alarm,the received system alarm as a target system alarm, wherein the receivedsystem alarm indicates that a user of a network file system (NFS) cannotaccess an NFS share; determining a system module corresponding to thetarget system alarm based on a predefined mapping relationship betweenthe system alarm and the system module, wherein the system modulecomprises a file interface and a server, wherein the system module is atleast one of multiple system modules, wherein the relationship betweenthe system alarm and the system module comprises a relationship betweenthe to-be-monitored alarm and the server and a mapping between thepredefined to-be-monitored alarm and the system module in a databasestored in a storage apparatus, and wherein the mapping between theto-be-monitored alarm and the system module is preset by a correspondingsystem developer responsible for developing and maintaining the systemmodule; and acquiring the system diagnostic information belonging to thesystem module and associated with the target system alarm, at least inpart by reproducing a problem event using a relevant operationassociated with the target system alarm, wherein the relevant operationis determined based on a system log entry of the system modulecorresponding to the target system alarm, and wherein the relevantoperation comprises a specific instruction that checks connectivity ofthe file interface and another specific instruction that checks bothconnectivity of the server and a configuration state of the server. 2.The method of claim 1, wherein acquiring the system diagnosticinformation comprises: acquiring the system log entry of the systemmodule corresponding to the target system alarm; and determining thesystem diagnostic information based on the system log entry.
 3. Themethod of claim 1, wherein acquiring the system diagnostic informationcomprises: acquiring detection data by detecting the system module basedon the target system alarm; and determining the system diagnosticinformation based on the detection data.
 4. The method of claim 3,wherein acquiring the detection data comprises: acquiring the system logentry of the system module corresponding to the target system alarm;determining the relevant operation associated with the target systemalarm from the system log entry; acquiring a state of the system modulewhen the relevant operation is performed; and generating the detectiondata based on the state.
 5. The method of claim 1, further comprising:outputting, in response to receiving an event fed back by a user andassociated with the target system alarm, the system diagnosticinformation for analysis.
 6. The method of claim 1, wherein the systemmodule comprises at least one of the following: a storage module, adisplay module, a computing module, and a network module.
 7. Anelectronic device, comprising: at least one processing unit; and atleast one memory coupled to the at least one processing unit and storinginstructions configured to be executed by the at least one processingunit, wherein when executed by the at least one processing unit, theinstructions cause the device to perform actions comprising:determining, according to determination that a received system alarmcorresponds to a predefined to-be-monitored alarm, the received systemalarm as a target system alarm, wherein the received system alarmindicates that a user of a network file system (NFS) cannot access anNFS share; determining a system module corresponding to the targetsystem alarm based on a predefined mapping relationship between thesystem alarm and the system module, wherein the system module comprisesa file interface and a server, wherein the system module is at least oneof multiple system modules, wherein the relationship between the systemalarm and the system module comprises a relationship between theto-be-monitored alarm and the server and a mapping between thepredefined to-be-monitored alarm and the system module in a databasestored in a storage apparatus, and wherein the mapping between theto-be-monitored alarm and the system module is preset by a correspondingsystem developer responsible for developing and maintaining the systemmodule; and acquiring the system diagnostic information of the systemmodule which is associated with the target system alarm, at least inpart by reproducing a problem event using a relevant operationassociated with the target system alarm, wherein the relevant operationis determined based on a system log entry of the system modulecorresponding to the target system alarm, and wherein the relevantoperation comprises a specific instruction that checks connectivity ofthe file interface and another specific instruction that checks bothconnectivity of the server and a configuration state of the server. 8.The device of claim 7, wherein acquiring the system diagnosticinformation comprises: acquiring the system log entry of the systemmodule corresponding to the target system alarm; and determining thesystem diagnostic information based on the system log entry.
 9. Thedevice of claim 7, wherein acquiring the system diagnostic informationcomprises: acquiring detection data by detecting the system module basedon the target system alarm; and determining the system diagnosticinformation based on the detection data.
 10. The device of claim 9,wherein acquiring the detection data comprises: acquiring the system logentry of the system module corresponding to the target system alarm;determining the relevant operation associated with the target systemalarm from the system log entry; acquiring a state of the system modulewhen the relevant operation is performed; and generating the detectiondata based on the state.
 11. The device of claim 7, wherein the actionsfurther comprise: outputting, in response to receiving an event fed backby a user and associated with the target system alarm, the systemdiagnostic information for analysis.
 12. The device of claim 7, whereinthe system module comprises at least one of the following: a storagemodule, a display module, a computing module, and a network module. 13.A computer program product having a non-transitory computer readablemedium which stores a set of instructions to acquire system diagnosticinformation; the set of instructions, when carried out by computerizedcircuitry, causing the computerized circuitry to perform a method of:determining, according to determination that a received system alarmcorresponds to a predefined to-be-monitored alarm, the received systemalarm as a target system alarm, wherein the received system alarmindicates that a user of a network file system (NFS) cannot access anNFS share; determining a system module corresponding to the targetsystem alarm based on a predefined mapping relationship between thesystem alarm and the system module, wherein the system module comprisesa file interface and a server, wherein the system module is at least oneof multiple system modules, wherein the relationship between the systemalarm and the system module comprises a relationship between theto-be-monitored alarm and the server and a mapping between thepredefined to-be-monitored alarm and the system module in a databasestored in a storage apparatus, and wherein the mapping between theto-be-monitored alarm and the system module is preset by a correspondingsystem developer responsible for developing and maintaining the systemmodule; and acquiring the system diagnostic information belonging to thesystem module and associated with the target system alarm, at least inpart by reproducing a problem event using a relevant operationassociated with the target system alarm, wherein the relevant operationis determined based on a system log entry of the system modulecorresponding to the target system alarm, and wherein the relevantoperation comprises a specific instruction that checks connectivity ofthe file interface and another specific instruction that checks bothconnectivity of the server and a configuration state of the server.